home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d20
/
farea10.arc
/
FIXAREAS.DOC
next >
Wrap
Text File
|
1991-02-04
|
4KB
|
88 lines
FIXAREAS.EXE Program Documentation
Copyright (c)1990 - Tom Beattie, FidoNet 1:104/522
First off, use this program at your own risk. I do not retain any
liability for anything that happens because of it's use... with the
exception that it works as promised and that you might possibly see fit
to register the program. Registration is $10US and may be mailed to
the address close to the end of this document.
Now, on to the good stuff!
Earlier this evening, I found that one of my utilities (ECHOLINK.EXE
for D'Bridge msg*.bbs linking) wasn't working properly and started
investigating the problem. Well, lo and behold after a couple of hours
staring at my monitor, I found that the AREAS.BBS file that Echolink
was looking at was not in the proper format! QLink.EXE helped me out
with that conclusion cause it wouldn't run either! This AREAS.BBS file
was created by a really nice new utility (I won't mention any names
here) that helps out a *LOT* with the editing of the Remote Access
Message and File Areas.
After I got about halfway through the code for this FIXAREAS utility, I
thought to myself, "Wow!, maybe someone else might be able to use this
seeing as how as long as you keep with the proper order when creating
an AREAS.BBS, you can then run FIXAREAS.EXE and it will read your file,
sort it, and then write it back out in the proper format for all the
utilities that use it!"
Well, Here it is! FIXAREAS.EXE!
You will have to do 2 things to make it work.
1. Place FIXAREAS.EXE somewhere in your path.
2. In each of the directories that you have an existing AREAS.BBS,
create a file called AREAS.HDR that contains two lines of information.
The first line is the name of your BBS, i.e. Rocky Mountain Wildcat
followed by a carriage return. The second line is Your Name, assuming
you are the SYSOP of course! i.e. Tom Beattie followed by a carriage
return.
THAT'S IT to the configuration anyway.
Now, go to the directory that contains your AREAS.BBS and AREAS.HDR
files and type FIXAREAS.
FixAreas will then read the AREAS.BBS and AREAS.HDR files, sort the
area information by area number, then write out a new AREAS.BBS file
with the proper format.
When creating or modifying your AREAS.BBS, having FIXAREAS.EXE on hand
greatly simplifies your editing. You no longer have to worry about the
spacing. Just enter the information in the proper order, i.e. Board# or
path, EchoTag, Nodes to Forward To, all seperated by one or more spaces,
run FIXAREAS and voila! You have a new AREAS.BBS file in the proper format.
NOTE: If any line in the original AREAS.BBS file is more than 256
characters, it will be truncated at that point. I am currently working
on a fix for this and anyone that registers FIXAREAS between now and
then will receive a fresh copy when it is available.
I have tried to think of all the possible combinations of AREAS.BBS
files but as a good friend of mine always says, "There's always at
least one more batchfile." So, if you do have any problems with
FIXAREAS.EXE, netmail me at 1:104/522 with a message explaining your
problem and file attach a copy of your AREAS.BBS so I can test it out.
THANKS! Hope you like it!
Tom Beattie
c/o KHOW/KSYY Radio
8975 E. Kenyon Ave.
Denver, CO 80237
CHANGES/MODIFICATIONS
1/22/91 - Added Support for Fido Style AREAS.BBS. Also, the registered
version will now create an alphabetical list of echotags for use with
AREAFIX. Say, if you get in a new AREAS.BBS type file from your STAR,
you can run FIXAREAS to create the list of available Echos from your
STAR.
Also, added some commandline parameters which are all optional. Type
FIXAREAS ? at the DOS prompt for a help screen.